RPD Editing Mode

1.   RPD Editing Mode

[supsystic-tables id=’3′]

1.1. Modifying the Oracle BI Repository

You can modify and extend the Oracle BI repository (RPD). This section provides information about RPD modification tasks. For some tasks, links to additional documentation are provided.

Task: Open the Oracle BI Administration Tool

The Oracle BI Administration Tool is a Windows application that you use to create and modify the RPD.

To open the Administration Tool, choose Start > Programs > Oracle Business Intelligence > BI Administration.

Note:

Do not open the Administration Tool by double-clicking a repository file. The resulting Administration Tool window is not initialized to your Oracle instance, and errors will result.

You can also launch the Administration Tool from the command line, as follows:

• In Windows Explorer, go to the location appropriate for your install type:
  • Client installations:
ORACLE_HOME/bifoundation/server/bin
  • All other installations:
ORACLE_INSTANCE/bifoundation/OracleBIApplication/coreapplication/setup
• Double-click bi-init.cmd (or bi-init.bat for client installations) to display a command prompt that is initialized to your Oracle instance.

At the command prompt, type admintool and press Enter.

2.   RPD Deployment (Logical Steps)

Step1:

Login into EM entering ->http://machinename:7001/em – Address needs to change according to environment.

Step2:

Once you logged into EM, Go to Business Intelligence from left side pane and select ‘core application’. Select repository from right side pane.

Go to ‘Deployment’ tab -> select ‘Repository’ tab -> click on ‘Lock and Edit’ option.

Step3:

Once you click ‘Lock and Edit Configuration’ you will get the confirmation message . Click ‘Close’ with the screen.

Step4:

So In the next screen you will have the options to select repository and catalog which you want to deploy. After you selected the rpd and catalog click apply and click Activate Changes. (ingore catalog in this case)

ORACLE_INSTANCE/bifoundation/OracleBIServerComponent/coreapplication_obisn/repository

Step5:

Choose the repository from the location and enter the repository password and change the catalog name.

Note: Do not forget to click ‘Apply’ button to save the changes .After the repository is uploaded, it is given a version number suffix (for example, SampleApp_bi001.rpd). After that Click ‘Activate Changes’

Step6:

Once you click ‘Activate Changes’ , Activation process will be started

After this process is over, It will show the confirmation window. Just click ‘Close’

Step7:

Once the changes has been activated, It will ask for the ‘Restart to apply recent changes’. Click ‘Restart to apply changes’

Step8:

Once you click ‘Restart to apply recent changes’/ Restart – then a pop up screen will come for confirmation. Click ‘Yes’ to restart all the BI Services. Once the services are successfully restarted, the repository is updated.

Step9:

Login into OBIEE entering ->http://xx.xx.xx.xx:7002/analytics/saw.dll?catalog then click New -> Analysis – > Select Subject Area -Make sure correct Subject Area has been populated (see example below)

3.   OBIEE 11g Project Lifecycle

Reference http://odtugspconference.com/Slides/OBIEE11g%20Deployment%20&%20Change%20Management%20Best%20Practices.pdf

3.1. Stage #1 – Early Days

• Prototype to first production
• Typically a single developer, no version-control
• Initial project is moved from DEV server into PROD once first phase complete

3.2. OBIEE 11g Project Lifecycle Stage #2 – Further Releases

• Updates to this first release, to add new RPD objects, shared folder catalog objects
• Incremental metadata needs to be merged into PROD, keeping existing objects
• Uses the three-way merge features for the RPD and the catalog

4.   Merging Repository Files (RPDs)

• Merging repositories is a common task on projects past the initial stage
  • To merge new and changed objects in DEV into the PROD repository
  • To merge two RPDs into one, to run online in PROD
• Common task in general software development projects, with common complications
  • Repositories may contain similarly-named objects, but logically different
  • Repository objects may have changed in both DEV and PROD – which do you choose?

These, and others, are called “merge conflicts”

4.1. Oracle BI Repository Three-Way Merges

• Oracle BI, like many software development tools, uses the concept of three-way merges
  • A modified repository, which is usually the PROD repository
  • A current repository, which is usually the DEV repository
  • An original repository, from which they were both derived
• Provides a number of benefits compared to 2-way merges
  • Avoids “guessing” whether objects with the same name are actually logically the same
  • For branching development, allows both branches
    to be updated with subsequent changes to the original
  • More accurate and efficient way of merging two sets of objects with common parentage
• If no common repository available, then substitute blank repository (and loose the 3-way merge benefits)

Three-Way RPD Merge Step 1 : Open Current RPD, Select Merge

• Start the BI Administration tool
  • Open the Current (typically, Development) repository offline • Select File > Merge…

With the Merge Repository Wizard – Select Import Files dialog open, select the modified (production) and original (common parent) RPDs

• Enter passwords
• Tick the Equalize during merge checkbox
• Select Full Repository Merge

Conflicts typically occur if a choice needs to be made between two options

• Select the choice either from the modified (prod) or current (dev) repository
• Choices can go down to the object property level
• Once all conflicts resolved, merged repository is then opened for editing